Skip to main content

TabMenu How To's

How to's for the TabMenu guide.

How to Use TabMenu?​

How to Use TabMenu?​

The following steps should be followed to create a tab-based structure on a form using the TabMenu object.

Add the TabMenu Object to the Form​

  1. Open the form design screen
  2. Go to the Toolbox panel
  3. Locate the TabMenu object
  4. Drag and drop the object onto the form

Define Tabs (Tab Items)​

  1. Select the TabMenu object
  2. In the Properties panel, locate the Tab Menu Items field
  3. Click the ... button next to it
  4. In the window that opens, click Add
  5. For each tab, fill in the following fields:
    • Name: Unique key of the tab
    • Text: Title visible to the user
    • Icon (optional): Tab icon
    • Selected: Default opened tab
    • Enabled: Whether the tab is active

Add Objects into Tabs​

  • After creating the tabs,
  • Activate the relevant tab
  • Drag and drop form objects (TextBox, DataGrid, Panel, etc.)
    into that tab

Each tab contains its own content independently.

Switch Between Tabs​

  • In the web interface, the user
  • Can click on tab titles
  • To instantly switch between tabs

Usage Tips​

  • Use TabMenu in forms that contain a large number of objects
  • Keep tab titles short and meaningful
  • Do not forget to set the default tab as Selected = true
  • Support tabs with icons to improve visual clarity

Notes​

  • Objects inside TabMenu behave like regular form objects
  • Switching between tabs does not cause data loss
  • For event handling, the On TabMenu Item Click event can be used

What Is TabMenu?​

What Is TabMenu?​

TabMenu is a form control that enables content to be logically separated by creating tabs on a form.
Each tab can contain different form objects, and users can switch between tabs by clicking on them.

With this structure:

  • Long and complex forms become more readable
  • Content is separated by topic
  • User experience is significantly improved

What Is It Used For?​

TabMenu is especially preferred in the following scenarios:

  • Dividing a form into multiple screens
  • Displaying different data groups under tabs
  • Allowing users to focus only on the relevant content
  • Creating dashboard-like tabbed interfaces

Example Use Cases​

  • General Information / Details / Attachments tabs
  • Personal Information – Contact – Authorization
  • Process Steps – Logs – Documents

Key Features​

  • Tab-based navigation
  • Independent content for each tab
  • Active / inactive tab management
  • Icon-supported tabs
  • Event triggering support

Notes​

  • TabMenu is a visual and navigational object only
  • It does not store data; it contains content
  • Objects inside it behave like regular form objects

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.